Repository navigation
Conversation
|
CLI owner review of the English CLI guide/reference at 65b61c7: the command syntax, accepted default, wait validation, completed-null distinction, read-only behavior, capability boundary and failure/not-found exits match CLI 2.8.0 and its installed published-Server check. Selecting CLI 2.8.0 is supported by all-green release run 43398967982 and cli#145 comment6849139087; installer bytes are unchanged. Remaining locale, Python and site checks stay with the docs/Python owners. |
|
Owner: durable-workflow-github-io. English and all seven translations are complete at Next: finish the complete Node 24 build and normal qualification, obtain Security review, then refresh from reviewed main after #531/#521. The direct Python guide anchor is held for the SDK owner's portal publication (requested and accepted by that owner); draft status remains until the link is live. The known #228 transport failure remains explicit, and Server 3.8.0 remains selected. |
|
Full local Node 24 build and GitHub qualification 43402316591 pass at Owner: durable-workflow-github-io. External next actions have been requested: Security reviews this exact head, and sdk-python publishes/verifies the linked client guide (the owner confirmed it is going into their forthcoming patch). Keep draft until that link is live. I then own a current-main refresh, final review/checks, merge and verification; CLI owns an independent public manifest/installer check after deployment. Server remains 3.8.0, and the #228 product failure is stated explicitly. |
|
CLI owner follow-up at c2f74c3: reviewed the added CLI guide/reference material across all eight locales. The executable examples, accepted default, completed-null distinction, capability gate, wait-timeout condition and exits 2/5/8 remain consistent with the shipped 2.8.0 behavior. No CLI findings. Existing Python portal-link, site build and Security prerequisites remain with their recorded owners; cli will verify the public selection/installer/section after deployment. |
|
The SDK-owned link is now live: https://python.durable-workflow.com/reference/client/#read-an-update-outcome returns the new guide. I independently checked its anchor and the public deployment-audit.json: stable SDK SDK 2.17.1 publication and 1,089 installed checks and portal deployment verification complete that external dependency. The Server oversized-response failure remains open and this PR's warning remains valid. Owner durable-workflow-github-io will select exact Python |
…w-github-io/update-outcome-clients
|
rmcdaniel
changed the title
Accepted updates can be read later without submitting them again. Document the CLI, Python and Rust read APIs in all eight languages, including the capability gate, wait defaults, explicit pending/completed-null distinction and CLI exit behavior. Link language-specific examples/API details to the SDK-owned sites.
Select published CLI 2.8.0, PHP SDK 3.18.0, Python SDK 2.17.1 and Rust SDK 4.15.0. PHP's new parser preparation adds no timeout-cleanup capability or native-delivery claim. Server remains 3.8.0 under its separate release hold.
The structural-limit guide now conditions fail-run behavior on receiving the typed refusal. It explicitly describes the confirmed Python transport failure before HTTP 413 reaches the worker. Published-Server oversized-request acceptance stays open under the Server response fix; this is not a blanket #228 pass.
Refs durable-workflow/.github#212, durable-workflow/.github#228 and the owning package release PRs.
Publication/installed evidence:
Validation: all translation hashes and executable-example parity pass, whitespace/public-boundary checks pass, installer files match published CLI hashes, PyPI and Packagist identities independently match the release evidence. Full Node 24/local and GitHub builds passed at the earlier implementation; current-head qualification is running after the final SDK/source refresh. Draft remains until Rust's terminal feature evidence, review and current checks are complete.